Notes on saying no

The first two years on my own I ran three projects at once, because three felt like the responsible number and because turning down work when you have no pipeline is a nerve I did not have.

The work was fine. All of it was fine. None of it was the reason anyone hired me.

What overlap costs

Two projects do not take twice as long as one. They take about two and a half times, and the extra half is spent reloading context — remembering where a decision came from, re-reading your own notes, rebuilding an argument you had already made once.

Worse, the reloading tax lands hardest on the part of the work that needs continuity: the long, unglamorous middle where a direction turns into a system. That is precisely the stretch that gets sacrificed when something else is on fire.

One at a time

Now it is one project, start to finish, with a queue and honest dates. Clients wait longer to start and the work arrives sooner, which sounds like a paradox for about a week.

How to say it

Quickly, and with a date. I am not free until March. If that works, I will hold it for you; if not, here are two people I would trust with this.

Nobody has ever been annoyed by that. Several have waited. The only version people mind is the slow no, which is why I answer within two days even when the answer is no.